About Linking
A Link-Group:
- Can contain up to 6 LQ devices or up to 6 of a combination of HelixNet Main Stations and LQ devices
- Must have one unit designated as Link-Master
- Performs a “best effort” approach to creating a mesh network between all the devices within the group.
The Link-Master role
The Link-Master role serves three main purposes:
- It facilitates Link-Group membership.
- It is the owner of Channel names, meaning that Channel names will only persist (be maintained consistently) if the Link-Master is operational.
- It is responsible for the synchronization and distribution of both configuration and device availability status throughout the Link-Group.
| Note: | The Link-Master must be reachable on TCP port 80 and TCP/UDP port 655 by all devices within the Link-Group. (Use TCP port 443 if you are using secure HTTPs.) |
| Note: | It is recommended that the IP address of the Link-Master is allocated statically. When allocated by DHCP the IP address can change. If this happens the LQ devices will no longer be able to reach the Link-Master device. |
| Note: | Any device can be set to Link-Master mode. Link-Master mode is the factory default setting. |
The Link-Member role
LQ devices that are not designated master will have the role of Link-Member. Joining a device to a Link-Group requires that device to be set to Link-Member role which will prompt the user to enter the address of the Link-Master.
If a Link-Member device loses connection to its Link-Master, the front panel LED of that device will turn red until the connection is restored.
Linking units
The only way to join devices to a Link-Group is through the Linking page of the CCM. Only the IP address of the Link-Master is required during this set up.
LQ restricted IP range
LQ units use the IP range 172.23.xx.xx for linking. Because of this, this IP range should not be used for any devices (including LQs) when working with the LQ Series system. Clear-Com cannot guarantee reliable behavior if this address range is used.
Linking over a LAN
This is the simplest way to link devices together. This type of environment enables the highest potential level of communication quality and the best availability of resources. When linking over a LAN, set Link-Group Optimization to LAN/WAN routed network in the Linking page of the Core Configuration Manager (CCM) for best latency performance and use of resources.
| Note: | External linking is disabled when Link-Group Optimization is set to LAN/WAN Routed Network. |
Linking over Internet or WAN
When linking over the public Internet, addressing of the Link-Master becomes more complicated as the Link-Master must be made externally reachable to all Link-Members. This is achieved by creating port forwarding rules within the firewall.
| Note: | A HelixNet/LQ Link-Group does not operate over the Internet. This is because the codec that HelixNet uses (WavPack) is not optimised for the Internet. Internet connectivity when using HelixNet and LQ is achieved using a tie line. |
How to link LQ units over a firewall
The Link-Master uses TCP port 80 for management and TCP/UDP port 655 for audio (port 443 for management if you are using HTTPs). You will need to create port-forwarding rules within your firewall to make these ports externally accessible to the Link-Master device.
When creating a Link-Group over the public internet, Link-Members need to be given the Link-Master’s externally reachable IP address and the port that is forwarded to port 80. This information is entered in the Linking page of the CCM.
| Note: | If no port forwarding rules have been applied the LQ devices will find the correct default ports automatically, so there is no need to specify a port. |
Once the devices are linked in a group, they will share network details with each other automatically. To facilitate this, the network details, including the port that is forwarded to TCP/UDP port 655 need to be configured in the Link-Master’s Network page. If no port forwarding rules have been applied, it is not necessary to specify a port.
For more information on linking over the Internet, see Internet Connectivity .
Related topics